The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Apr 15, 2026 11:08pm

PR Summary

Medium Risk
Touches external-tool execution paths and output shaping (including new polling behavior), which could affect runtime timing and downstream workflows relying on Bright Data tool outputs.

Overview
Fixes brightdata_discover to handle Bright Data’s async flow by returning taskId from the initial POST and adding a postProcess polling loop (with logging + timeout) to fetch final results.

Updates multiple Bright Data tools’ transformResponse to use the passed params for echo-back outputs (snapshotId, url, query, searchEngine) instead of hardcoded null or parsing unreliable response fields, and extends the BrightDataDiscoverResponse type to include optional taskId.

Minor cleanup: reorders box in the block registry to maintain alphabetical ordering, changes the Agiloft docs info card color to white, and updates bun.lock metadata.

^{Reviewed by Cursor Bugbot for commit 9e9bf35. Configure here.}

Greptile Summary

Fixes the BrightData Discover tool to use the async POST→poll-GET pattern (the API returns a task_id immediately, results arrive via polling), and corrects echo-back fields across five tools that were returning null or reading unreliable response body fields instead of using params. Registry alphabetization and Agiloft docs color are also tidied. The two previously flagged issues (taskId type safety, hardcoded polling timeout) are both resolved in this revision.

Confidence Score: 5/5

Safe to merge — all remaining findings are P2 style suggestions that don't block correct behavior.

The two prior P1 issues are resolved, the polling implementation follows the established Firecrawl pattern, and the echo-back fixes are clean. Remaining comments (poll error body, content fallbacks) are speculative improvements that don't affect the core correctness of the fix.

apps/sim/tools/brightdata/discover.ts — poll error message and content field fallbacks worth a second look before merging.

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant W as Workflow Executor
    participant T as brightDataDiscoverTool
    participant BD as BrightData API

    W->>T: execute(params)
    T->>BD: POST /discover (query, intent, ...)
    BD-->>T: { task_id: "abc123" }
    T->>T: transformResponse → output { taskId, results: [] }

    Note over T: postProcess polling loop
    loop every 3s until MAX_POLL_TIME_MS
        T->>BD: GET /discover?task_id=abc123
        BD-->>T: { status: "pending" }
    end
    T->>BD: GET /discover?task_id=abc123
    BD-->>T: { status: "done", results: [...] }
    T->>T: map results → { url, title, description, relevanceScore, content }
    T-->>W: { success: true, output: { results, query, totalResults } }

_{Reviews (3): Last reviewed commit: "fix(brightdata): use platform execution ..." | Re-trigger Greptile}

@greptile

@cursor review

@greptile

@cursor review